Shareware Super Platinum 8

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Super Platinum 8 / Shareware Super Platinum 8.iso / mac / ARCHIVE / ZL2B0117.ZIP;1 / ZIPLAB.DOC < prev next >

Wrap

Text File | 1993-01-17 | 49.1 KB | 1,065 lines

±±±±±±±±±‹ ±±±±‹ ±±±±±±±±±‹ ±±±±‹ ±±±±±±±±‹ ±±±±±±±±±‹ ﬂﬂﬂﬂﬂ±±€ﬂ ±±€ﬂ ±±€ﬂﬂﬂ±±€ ±±€ﬂ ±±€ﬂﬂﬂ±±€ ±±€ﬂﬂﬂ±±€ ±±€ﬂ ±±€ ±±€ ±±€ ±±€ ±±€ ±±€ ±±€ ±±€ ±±±€ﬂ ±±€ ±±±±±±±±€ ±±€ ±±±±±±±±€ ±±±±±±±€ﬂ ±±€ﬂﬂ ±±€ ±±€ﬂﬂﬂﬂﬂﬂ ±±€ ±±€ﬂﬂﬂ±±€ ±±€ﬂﬂﬂ±±€ ±±€ﬂ ±±€ ±±€ ±±€ ±±‹ ±±€ ±±€ ±±€ ±±€ ±±±±±±±±±‹ ±±±±€ ±±±±€ ±±±±±±±±±€ ±±±±€ ±±±±€ ±±±±±±±±±€ ﬂﬂﬂﬂﬂﬂﬂﬂﬂ ﬂﬂﬂﬂ ﬂﬂﬂﬂ ﬂﬂﬂﬂﬂﬂﬂﬂﬂ ﬂﬂﬂﬂ ﬂﬂﬂﬂ ﬂﬂﬂﬂﬂﬂﬂﬂﬂ ±±±±±±±±±‹ ±±±±‹ ±±±±‹ ±±±±‹ ±±±±±±±±‹ ±±€ﬂﬂﬂ±±€ ±±€ﬂ ±±€ﬂ ±±€ﬂ ±±€ﬂﬂﬂ±±€ ±±€ ±±€ ±±€ ±±€ ±±€ ±±€ ﬂﬂ ±±±±±±±±€ ±±€ ±±€ ±±€ ±±±±±±±±‹ ±±€ﬂﬂﬂﬂﬂﬂ ±±€ ±±€ ±±€ ﬂﬂﬂﬂ±±€ ±±€ ±±€ ±±‹ ±±€ ±±€ ±±‹ ±±€ ±±±±€ ±±±±±±±±±€ ±±±±±±±±€ ±±±±±±±±€ ﬂﬂﬂﬂ ﬂﬂﬂﬂﬂﬂﬂﬂﬂ ﬂﬂﬂﬂﬂﬂﬂﬂ ﬂﬂﬂﬂﬂﬂﬂﬂ ±±±±±±‹ ±±±±±±‹ ﬂﬂﬂ±±€ ±±€ﬂ±±€ ±±±±±±€ ±±€ ±±€ ±±€ﬂﬂﬂﬂ ±±€ ±±€ ±±±±±±‹ ±±‹ ±±±±±±€ ﬂﬂﬂﬂﬂﬂ ﬂﬂ ﬂﬂﬂﬂﬂﬂ Copyright (C)1989-93 by Jeffrey S. Morley ZipLab PLUS Version 2.·.9 (C)Copyright 1989-93 by Jeffrey S. Morley January 17th, 1993 Archive testing and maintenance program for PCBoard/ProDoor Sysops. ############################################################################## Table of Contents ############################################################################## To jump to a section, do a search on the page number in the format: "Pgx" where "x" is the page number to jump to. Introduction to ZipLab Plus 2.0 .......................................... 1 Installation of ZipLab / Requirements .................................... 2 Installation of ZipLab / Quick Start ..................................... 3 Installation of ZipLab / A Sample Configuration File ..................... 8 Installation of ZipLab / Configuration Details ........................... 9 I. Conference Specific Configurations ......... 9 II. ZLABxxx.TCN Trashcan File(s) ............... 10 III. ZLABxxx.CMT Comment File(s) ................ 10 IV. CRC.ADS .................................... 10 V. LST.ADS .................................... 11 VI. *.MSG The Message Files .................... 11 V. PKZIP 2.0 .................................. 12 Installation of ZipLab / Usage Notes and Warnings ........................ 13 I. Command Line Parameters .................... 13 II. PCBoard's TEMP Directory ................... 13 III. ZipLab's WORK Directory .................... 14 IV. Using Giftest with ZipLab .................. 14 Installation of ZipLab / Some Notes on Memory Usage ...................... 16 Installation of ZipLab / ProDoor Differences ............................. 17 ZipLab Plus Version History .............................................. 19 About ZipLab Plus and the Author ......................................... 20 Pg1 ############################################################################## INTRODUCTION TO ZIPLAB PLUS ############################################################################## What is ZipLab Plus? ZipLab Plus is a shareware program which will test archived files. In addition, ZipLab will allow you to add .ZIP comments, strip out unwanted members, and much, much more! ZipLab was designed for PCBoard/ProDoor SysOps, to test files as they are uploaded to their systems. It is run in the PCBTEST.BAT file which comes with PCBoard 14.5. PCBTEST.BAT is run by PCBoard when an upload completes. The following is a quick list of ZipLab's features: Testing: * Test for CRC errors in the archive file. * Test for imbedded archive files and if found, CRC check those too. * Test for imbedded .TD0 (Teledisk) files and if found, test with TDCHECK. * Virus check archive member files, using your favorite virus checker. * Virus check inside archive files imbedded inside another archive file. * Test .GIF files for validity if you accept that file format (Optional) * Run virus check on files which you optionally pass without ZIP testing. * Reject programs older than a date (yyyymm) which you specify. * Uses a "trashcan" file to reject by description keywords you specify. * Will fully test "self-extracting" archives of the ZIP/ARJ/LZH formats. Maintenance: * Remove all archive comments from the file. * Replace archive comments with your own. (Optional) * Add the contents of FILE_ID.DIZ to the archive comment. * Use special ZipLab "@" codes to include test information in the comment. * Adds the reasons to the comment on files which fail ZipLab Plus testing. * Delete unwanted BBS ads and/or other unwanted archive members as you define. - ZipLab tests for BBS ads by FILENAME or file CRC. * Allows you to optionally add a file to the archive. PCBoard/ProDoor BBS specific features: * Add the resolution of .GIF files to the description (Optional) * Adds most recent archive member date to the description (Optional) * Optionally replace the description left by the user if FILE_ID.DIZ is found in the archive file. Formatted to the correct 45 char standard. * Will make a notation in both the CALLER file and the private DIRx file for the current node of any files which fail upload testing, including the failure reason. * Allows your users to run the TEST command in PCBoard to test files, but ZipLab will not remove the file unless it fails CRC or virus checking. You will be notified via the node's CALLER file of archives which fail PCBoard's TEST command, and why. * Takes the phone "offhook" if the user hangs up before/during testing. * Sends a mail message to the user letting him know why a file was rejected, and to both the user and the Sysop when a virus is found. * Allows full conference specific configurations. General: * Run the full range of tests on .ZIP, .LHZ and .ARJ archive formats * Works on a PCBoard/ProDoor BBS in both online and local modes. * Works with both the old and new versions of PKZip. Pg2 ############################################################################## ZIPLAB PLUS REQUIREMENTS ############################################################################## ! YOU MUST BE RUNNING PCBOARD VERSION 14.5(a) OR PRODOOR VERSION 3.44 ! You must have the following programs. Several are included in the ZipLab Plus archive, but registration of ZipLab DOES NOT include registration of any of these products. Please SUPPORT SHAREWARE and register these products with their respective authors. PKZIP.EXE - Phil Katz's archive create program (version 1.01 or 1.93) PKUNZIP.EXE - Phil Katz's archive extract program (version 1.01 or 1.93) LHA.EXE - Yoshi's archive program (version 2.13 +) ARJ.EXE - Robert Jung's archive program (version 3.00 +) SCAN.EXE * - McAffey's virus detection program (any version) RECOM.EXE - Mike Loewen's ZIP file comment remover GIFTEST.EXE - Dave Navarro's .GIF file tester (optional) TDCHECK.EXE - .TD0 (Teledisk) checker from SyDex (optional) VBDTR10.EXE - RunTime module for Visual Basic for DOS. You will need this module in a directory in your DOS PATH to run ZSET.EXE. Free from Microsoft Inc. * Note! This can be replaced with the virus checking program of your choice, subject to restrictions and requirements outline in the installation guide. Programs I have written and which are part of the ZipLab Plus package. DELF.COM - A version of DEL with no "Are you sure?" prompt. ZLSCR.COM - A little utility called by ZipLab to help handle the local screen during testing (Based on ProNS.COM by Sam Smith). ZCRC.EXE - A small utility to get file CRC values for placement in your ADS.CRC file. ZLAB.EXE - The ZipLab Plus executable program. ZSET.EXE - The ZipLab Plus setup/configuration maintenance program. Pg3 ############################################################################## QUICK START ############################################################################## * ZipLab does a LOT of things. It is a complicated program, but a breeze to set up and run... IF you follow the directions and read this entire documentation. Print this document and follow it step by step. You can't miss. * Create a directory to hold ZLAB.EXE, the sample ZLAB000.CFG, ZLAB000.TCN, CRC.ADS, LST.ADS, *.MSG, ZLAB000.CMT and ZSET.EXE files. This directory should be in your DOS PATH. All ZipLab files can be shared by multiple nodes. Node specific configurations are not required. Let's assume you use C:\ZIPLAB for now. * UnZIP the enclosed supplemental utilities into directories in your DOS PATH. Make note of where you put them, you will need this information later. Make sure VBDRT10.EXE is in your DOS PATH. * Run "ZSET.EXE ZLAB000.CFG". ZSET will then start with the default configuration, ZLAB000.CFG, which you should modify to meet your system's needs. The "000" in the config name is conference specific. The default is for conference "0", the "Main Board". More later on how to create conference specific configurations. for now, ZipLab will default to looking for ZLAB000.CFG when run from any conference. * Modify the following information for your system ,in ZLAB000.CFG: 1 - The type of modem HANDSHAKE you desire. This can be 0, 1, 2 or 3. 0=none, 1=XON/XOFF, 2=CTS, 3=CTS & XON/XOFF (Use 2 or 3 with an error correcting modem...) DEFAULT = 3 2 - The name of your BBS system. 43 characters maximum. DEFAULT = THE INTERCONNECT BBS 3 - The DRIVE and PATH to the directory where rejects will be placed pending manual sysop inspection. This can be a common directory on multiple node systems, but SHOULD be an empty (existing) directory dedicated to this purpose. I recommend "d:\FAIL" or "d:\HOLD" as likely names. DEFAULT = C:\FAIL 4 - The full DRIVE\PATH\FILENAME of your ZLAB000.TCN (trashcan) file. The filename need not follow the ZLABxxx.ext format, but it will make conference specific work much easier later. DEFAULT = C:\ZIPLAB\ZLAB000.TCN 5 - The date (yyyymm) which will be the minimum accepted year. ZIPs containing files older than this will be rejected. Example: 199001 would mean any file older than January, 1990 would fail. DEFAULT = 199001 6 - A "Y" if you wish to replace the description left by the user with the contents of FILE_ID.DIZ (if found in the archive). A "N" if you do not wish to make use of this feature. DEFAULT = Y Pg4 7 - A "Y" if you wish the "recent date" notation added to the file descriptions. A "N" if you do not wish this addition. DEFAULT = Y 8 - A "Y" if you wish the "number of archive member files" notation added to the file descriptions. A "N" if you do not. DEFAULT = Y 9 - A "Y" if you wish ZipLab to send a mail message to the user when a file fails testing. A "N" if not. DEFAULT = Y 10 - A "Y" if you wish the sysop to also receive a mail message in the instance of a virus detection. A "N" if you do not. DEFAULT = Y 11 - The DRIVE\PATH\ to the directory which will hold the .MSG files. These are the mail messages sent to the user/sysop on failure. Please put a "\" at the end of the path. DEFAULT = C:\ZIPLAB\ 12 - The full DRIVE\PATH\FILENAME of a zip comment to add. Again, it is recommended that the name ZLAB000.CMT be used for consistancy. Specify "NONE" if you don't want to add a comment. DEFAULT = C:\ZIPLAB\ZLAB000.CMT 13 - A "Y" if ZipLab should add the contents of FILE_ID.DIZ (if found) to the bottom of the zip comment. "N" to disable. DEFAULT = Y 14 - The fully qualified filename of a file which you may wish to add to the .ZIP, or "NONE" (please!) if you can refrain from this practice. Once again, ZLAB000.ADD will make sense later. DEFAULT = NONE 15 - Full DRIVE:\PATH\FILENAME of PKZIP.EXE. DEFAULT = C:\UTILITY\PKZIP.EXE 16 - An optional list of extra parameters you wish to pass to PKZIP.EXE on the command line. If you are using PKZIP 2.0, use the command line parameter additions as suggested in the example ZLAB000.CFG that follows. Some PKZIP 2.0 switches: -) Turn off DMPI memory usage -- Turn off XMS memory usage -+ Turn off EMS memory usage -3 Turn off 386cpu specific code -~ Turn off NETWORK specific code -( Uses slower form of memory handling "NONE" will cause ZipLab not to pass any extra parameters. If you are using PKZip 1.1, NONE is appropriate. 17 - An optional list of extra parameters you wish to pass to PKUNZIP.EXE on the command line. If using PKUNZIP 2.0, use the command line parameter additions as suggested in the example ZLAB000.CFG that follows. Some PKUNZIP 2.0 switches: Pg5 -) Turn off DMPI memory usage -- Turn off XMS memory usage -+ Turn off EMS memory usage -3 Turn off 386cpu specific code "NONE" will cause ZipLab not to pass any extra parameters. If you are using PKZip 1.1, NONE is appropriate. 18 - Full DRIVE:\PATH\FILENAME of PKUNZIP.EXE. DEFAULT = C:\UTILITY\PKUNZIP.EXE 19 - Full DRIVE:\PATH\FILENAME of LHA.EXE. DEFAULT = C:\UTILITY\LHA.EXE 20 - Full DRIVE:\PATH\FILENAME of ARJ.EXE. DEFAULT = C:\UTILITY\ARJ.EXE 21 - Full DRIVE:\PATH\FILENAME of TDCHECK.EXE. (or "NONE" if not using) DEFAULT = C:\UTILITY\TDCHECK.EXE 22 - Full DRIVE:\PATH\FILENAME of SCAN.EXE, or another virus checker program. Be sure the program you may chose (other than SCAN) is appropriate for ZipLab. It MUST have reasonably memory requirements, allow for automatic command line use, and return a DOS ERRORLEVEL on virus detection. I do not warrent that any virus checker other than SCAN or F-PROT will work correctly. DEFAULT = C:\UTILITY\SCAN.EXE 23 - Optional command line switches to pass to the virus checker. Be sure you have read the docs for the program you use. As with the program in general, I only warrent that the switches I have used as an example for SCAN or F-PROT will work correctly. If you decide to use something else, be sure you understand and have tested any switches you provide. I do feel confident that these work: SCAN /NOMEM /NOBREAK /NOEXPIRE /NOPAUS F-PROT /NOMEM /NOBREAK /OLD Do NOT set a switch which causes the virus checking program to delete or rename the file. ZipLab will take care of that. "NONE" will cause ZipLab to not pass any parameters except the filename to test. DEFAULT = /NOMEM /NOBREAK /NOEXPIRE /NOPAUSE 24 - The DOS ERRORLEVEL which is set by your virus checker if a file virus is detected. This can only be ONE number, and unlike DOS, it is not a function of "more than this number". It is EXACTLY this number. Again, I have tested this with SCAN and F-PROT, but have no idea if any other virus checkers return appropriate ERRORLEVELs. The ERRORLEVELS set on virus detection for the two programs that I have tested are: SCAN 1 F-PROT 3 DEFAULT = 1 Pg6 25 - Full DRIVE:\PATH\FILENAME of RECOM.EXE. DEFAULT = C:\UTILITY\RECOM.EXE 26 - Full DRIVE:=PATH\FILENAME of DELF.COM DEFAULT = C:\UTILITY\DELF.EXE 27 - Full DRIVE:\PATH\FILENAME of GIFTEST.EXE (or "NONE" if not using) DEFAULT = C:\UTILITY\GIFTEST.EXE 28 - Command line PARAMETERS you wish to pass to GIFTEST.EXE Please refer to the documentation for GIFTEST for details! Just enter "NONE" if you do not desire to pass parameters. DEFAULT = NONE 29 - A list, all on one line, (separated by ";" - EXE;TXT;GIF) Which will be passed without normal ZIP testing. SCAN and date checking will still be performed on these files. Any extensions other than ZIP/ARJ/LZH which do not appear in this list will be rejected by the process. If GIF appears in this list, GIFTEST will be used to test the integrity of the GIF file. If you enter a "*" as one of the extentions, then ALL files will be passed through, with non-archived files being SCAN'd and date checked only. "NONE" in this position will only allow ZIP/ARJ/LZH files to pass. DEFAULT = GIF;EXE;PCX 30 - The full DRIVE/PATH/FILENAME of a text file containing the file CRC for files you wish removed before posting the archive. This file can be called anything, but LST.ADS works for me. You can use the included ZCRC.EXE to help maintain this file. More on the use of ZCRC.EXE later. DEFAULT = C:\ZIPLAB\CRC.ADS 31 - The full DRIVE/PATH/FILENAME of a text file containing the NAMES (one on each line) of files you wish removed before posting the archive. This file can be called anything you wish, I suggest CRC.ADS. Any files listed in this text file which exist in the uploaded archive will be removed. DEFAULT = C:\ZIPLAB\LST.ADS * Click on the "SAVE" button in ZSET.EXE, and save under the ZLAB000.CFG filename. * Edit your existing PCBTEST.BAT file, and delete the whole thing except for two lines: Sample PCBTEST.BAT file: @ECHO OFF C:\ZIPLAB\ZLAB.EXE %1 C:\PCB C:\ZIPLAB %2 ^1 ^2 ^3 ^4 1) %1 PCBoard will populate this with the DRIVE\PATH\FILE to test. 2) C:\PCB The PCBoard "home" directory for the node. 3) C:\ZIPLAB The directory containing your ZLABxxx.CFG file(s). 4) %2 PCBoard will populate this with TEST if a user is running the TEST command on the board. You can also pass LOCAL to this parameter to run ZipLab from DOS. Pg7 * Note! Although ZipLab can share its configuration files, it should be run FROM the PCBoard "home" directory of each node. Do not change directories in PCBTEST.BAT to your "ZIPLAB" directory. * That's it... Now when PCBTEST.BAT is run by PCBoard, it will pass command over to ZLAB.EXE with the parameter containing the path and name of the file to be tested. ZLAB will check out the file, placing any rejects in the holding directory you specified in the ZSET process above. Pg8 ############################################################################## A SAMPLE ZLAB000.CFG FILE ############################################################################## 2 The Interconnect Bulletin Board System C:\FAIL C:\ZIPLAB\ZLAB000.TCN 199001 Y Y Y Y Y C:\ZIPLAB\ZLAB000.CMT Y NONE C:\UTILITY\PKZIP.EXE -) -- -+ -3 -~ -( C:\UTILITY\PKUNZIP.EXE -) -- -+ -3 C:\UTILITY\LHA.EXE C:\UTILITY\ARJ.EXE C:\UTILITY\TDCHECK.EXE C:\UTILITY\SCAN.EXE /NOMEM /NOBREAK /NOEXPIRE /NOPAUSE 1 C:\UTILITY\RECOM.EXE C:\UTILITY\DELF.COM C:\UTILITY\GIFTEST.EXE /B:2 /F:UPDESC.2 GIF;EXE;PCX C:\ZIPLAB\CRC.ADS C:\ZIPLAB\LST.ADS Pg9 ############################################################################## CONFIGURATION DETAILS ############################################################################## I. Conference Specific Configurations You MUST at least have created a file name ZLAB000.CFG for ZipLab Plus to operate. The "000" tells ZipLab that this is the configuration file for the Main Board Conference, but is also the default for any conferences that do not have specific configuration files. To create a configuration for another conference (let's use your "GAMES" conference, number "5", as an example), run ZSET ZLAB000.CFG to bring in your default configuration file, and then modify the file to be specific to your Games Conference. You can change just about every configuration item to be specific to the Games conference. Some things you might want to change are: * The "Board Name" field - Maybe It will say "Joes BBS - Games Conference" * The name of your .TCN (trashcan) file. You may want to exclude more (or less) types of files from this conference. Just call the file ZLAB005.TCN. * The "Date Limit" field. Maybe you want only the LATEST games. * The "Zip Comment" field. Have a conference specific .ZIP comment by changing the name to ZLAB005.CMT. * The use (or non-use) of GIFTEST.EXE, and the acceptance of .GIF files. Once you have modified the configuration to your satisfaction, just click on "SAVE". You will be presented with a "windows-ish" file save dialog window. Change the name of the file to ZLAB005.CFG in the input field labeled "File will be saved as:", and click on "OK" (To edit this configuration file at a later time, just run ZSET.EXE with the name of the configuration file as a parameter. "ZSET ZLAB005.CFG") Make further changes for other conferences you wish to set up, and save under their respective names(up to 999 conferences). When done, exit ZSET.EXE. * Note! Be sure that any files like ZLAB005.TCN or ZLAB005.CMT that you specify actually do exist! You can create them before or after you run ZSET.EXE, but certainly before you run ZipLab Plus (unless you want to test my error handling system <g>). II. ZLABxxx.TCN The "trashcan" file(s) This file holds text key-words or key-phrases which are used to reject files based on either the filename or contents of the file description. If you for instance did not want "adult" .GIF files uploaded to your system, but did want to allow other .GIF file uploads, you might put the following lines in ZLAB000.TCN: ADULT X-RATED "X RATED" MARGARINE "KITCHEN TABLE" Pg10 Or whatever you feel would allow ZipLab to identify the kind of files you have in mind, without being so generic as to cause perfectly acceptable files to fail. ZipLab Plus will test the filename, user supplied description, and the contents of FILE_ID.DIZ (if found) against this list, and will reject any files which contain these "trashcan" words/phrases. * Note! To imbedd "white space" either in, before, or after an entry, use the QUOTE (") character to surround the phrase or word. For instance, if you wanted to exclude files with the word "WIN" in them, you should use " WIN " so that things like "TWIN" or "WINNER" don't also fail. III. ZLAB000.CMT The "comment" file(s) This is a text file which will be added as a .ZIP (or .ARJ) comment to the archive file. As you can see from the filename format, you can certainly have a different comment file for each conference if you so desire. This file can say anything you want. I have also included some ZIPLAB- specific "@ZCODES" which can be imbedded in the text to add information which ZipLab Plus will provide at run-time. You may NOT use PCBoard's "@-Codes", only the ones that ZipLab Plus supplies: @ZCODE MEANING FORMAT / ADDITIONAL DESCRIPTION @F_N@ File Name "filename.ext" @A_T@ Archive Type ".ZIP", ".ARJ", or ".LZH" @D_T@ Date Tested "mm/dd/yyyy" @T_T@ Time Tested "hh:mm:ss" @B_N@ Board Name from ZLABxxx.CFG @U_N@ User Name "firstname lastname" @N_O_F@ Number of Files count of files in archive @N_F@ Newest File "mm/dd/yyyy" @O_F@ Oldest File "mm/dd/yyyy" @P_F_S@ Pass-Fail Status "passed" or "failed" @R_F@ Reason for Failure "CRC checking" , "Virus checking" etc... @T_C_T@ Trash Can Text Text which failed .TCN checking - if any. @V_N@ Version Number Version of ZipLab Plus ("2.0") @D_L@ Date Limit "mm/dd/yyyy" @F_I_F@ FILE_ID.DIZ Found "found" or "not found" @N_N@ Node Number BBS node number @C_N@ Conference Number conference the user is in (as a number) * Note! You may also use the word "ZIPLAB" in this field in ZLABxxx.CFG, and ZipLab will create a comment for you, with much of the above information. As always, you may also use "NONE", and ZipLab will not add any comment at all. IV. CRC.ADS This file will contain the file CRC-32 values (and names) of files which you wish removed from the archive prior to posting. The format of the file is: 00000000,filename.ext Pg11 Where "00000000" is the file's CRC-32, and filename.ext is one of the names by which the file is known. The filename is not optional, but can really be anything, as ZipLab could care less what a file is called. If it matches on the CRC-32 value, it WILL be removed. You will want to maintain your CRC.ADS file using the ZCRC.EXE file which is included in the ZipLab Plus archive. Just type: "ZCRC [d:\path\]CRC.ADS [d:\path\]filename.ext" and ZCRC.EXE will place the proper information for the filename you replace "filename.ext" with at the bottom of the CRC.ADS file. As always, a "NONE" in the ZLABxxx.CFG file in this position will cause ZipLab Plus to skip this process. * Note! It is certainly acceptable to have different "CRC.ADS" files for different confereneces, and you could use the "ZLABxxx.ADS" convention if you wish. I find that trying to maintain multiple versions of this file to be a fair amount of trouble however, and don't particuarly recommend it. V. LST.ADS This is a text file (one on each line) containing only the names of files you wish removed without testing. The difference between this file and the CRC.ADS file is that you can test for a particular file name, and it will remove it even if the person adding the file changes the contents from time to time. This file also supports "wildcards", so you can test for those names where "special" characters (above 126 ASCII) have been used to create a filename, by masking out those characters. As an example, you could test for a BBS ad called "SúãM‰.PãÁ" by adding "S??M?.P??" as an entry in LST.ADS (of course, "SIMMS.PAS" would fail as well, so be careful how you use wildcards.). Use "NONE" in the field in ZLABxxx.CFG to disable this feature. * Note! This file can contain up to 100 lines in version 2.0. VI. *.MSG The mail message files The mail message files are text files (the @ZCodes can be used, and in fact you could imbedd PCBoard's @Codes as well, they will just get passed through to the message and handled by PCBoard when the user reads the message.), which will constitute mail messages sent to the user when a file fails. This can be used to tell the user the reason for the rejection, to remind him of rules you may have about types of file you accept, or to reassure him that you still love him even though his file did have a CRC error <g>. Remember when modifying or creating these files, that there are limits on mail messages in PCBoard. Also, be sure to leave enough room for any @ZCodes to expand to actual values without running longer than 78 characters per line. The files MUST have the names below, and samples of all the files are included in this archive. These files should be in a central location, perhaps the C:\ZIPLAB directory where you have the .TCN, .CMT and other ZipLab files is best. One of the entries in the ZLABxxx.CFG files will let you tell ZipLab where to find these files. Pg12 The files (and failure reasons) that ZipLab Plus uses are: NAME OF FILE REASON FOR FAILURE ------------ ------------------ OLDDATE.MSG Failed date limit checking FILECRC.MSG Failed CRC or -AV checking IMBEDCRC.MSG An imbedded archive failed CRC or -AV checking TRASHCAN.MSG .TCN (Trashcan) text was found in the description BADTD0.MSG A Teledisk format (.TD0) file failed TDCHECK USRVIRUS.MSG Message sent to USER on virus detection SYSVIRUS.MSG Message sent to SYSOP on virus detection UNACCEPT.MSG An unaccepted file format was uploaded GIFFAIL.MSG A .GIF file failed GIFTEST DO NOT RENAME THESE FILES! V. PKZIP 2.0 There have been found to be problems with PKZIP 2.0 and some hardware. If you have problems with PKZIP 2.0 and ZipLab. you should use the command line parameters in the example .CFG file in this documentation (Page 7). These command line parameters will disable certain "advanced" memory functions of PKZIP and PKUNZIP. The command line parameters are explained in the detailed section about the ZLABxxx.CFG file (Pages 4 and 5). NOTE! There are two switches "-~" and "-)" shown for PKZIP.EXE and not for PKUNZIP.EXE. PKUNZIP.EXE does not support (or require) these switches, and their use will cause an error. NOTE! DO NOT PASS THE ACTUAL COMMAND FUNCTION (like -a or -d for PKZIP / -x or -v for PKUNZIP) on this line of extra parameters. ZipLab will pass the appropriate primary command parameter. You should only send extra switches which change the operation of PKZIP or PKUNZIP. READ THE DOCS FROM PKWARE BEFORE USING OPTIONS OTHER THAN THOSE IN THE SAMPLE! READ BOTH MANUAL.DOC AND ADDENDUM.DOC WHICH CAME IN PKZ204C.EXE. IF IN DOUBT, DON'T DO IT! Pg13 ############################################################################## USAGE NOTES AND WARNINGS ############################################################################## I. Command line parameters - ZLAB.EXE has the following commmand syntax: ZLAB d:\path\filename d:\pcbpath d:\cfgpath [LOCAL|TEST] d:\path\filename - The file to test, normally passed by PCBoard. d:\pcbpath - The "home" PCBoard directory for this node. d:\cfgpath - The directory containing your ZLABxxx.CFG files. LOCAL - Causes ZipLab to function without any output to the comm port. Use this for testing files already on your hard drive, or that you have downloaded yourself and wish to post. No changes will be made to any DIRx files. TEST - PCBoard will pass this as %2 if you are using the TEST command inside PCBoard. Files will only be moved to the "hold" directory if they fail CRC or Virus checking. No changes will be made to any DIRx files. Normal comm port output. ZSET.EXE has the following command syntax: ZSET [d:\path\][configname.cfg] [d:\path\] - If you are not in the directory containing the .CFG files for the node, you must specify the exact location of the config file you wish to modify. [configname.ext] - The name of the ZLABxxx.CFG file you wish to load. This MUST be in the "ZLABxxx.CFG" format, with the "xxx" replaced with the conference specific .CFG file you wish to modify. {default} - If you do not specify a file on the command line, ZSET.EXE will create a file called "NONAME.CFG" in your current directory. After you have modified the default settings to your specifications, be sure to save the file under a proper ZLABxxx.CFG filename for the conference you are setting up, and in the proper location. NONAME.CFG will be deleted when you exit. II. PCBoard's "TEMP" directory - Line 179 of your PCBOARD.DAT file (maintained with PCBSETUP.EXE) is critical to the operation of ZipLab Plus. This is the "temporary" directory in which (among other things) PCBoard holds the file descriptions for uploads before they are actually posted. This directory MUST exist, and be EMPTY (don't use your root directory of your boot drive like a couple of people have in the past!). PCBSETUP WILL NOT CREATE THIS DIRECTORY WHEN YOU EXIT, even though it does create just about every other directory you specify if it doesn't exist. This is just a quirk of PCBSETUP, and it is up to you to be SURE this directory is both in PCBOARD.DAT and that it exists. Pg14 III. ZipLab Plus' "WORK" directory - This directory is created (and removed) each time ZipLab Plus runs. It is used to hold unzipped files and other temporary files while ZipLab is running. By default, ZipLab creates a new directory under your current one (your PCBoard root directory in most cases) called .\ZLAB.DIR, which it removes when done. If you want to redirect this to another drive (say a RAM drive for additional speed), set an environment variable called "ZIPLAB" to the drive and directory name you wish. SET ZIPLAB=E:\ZWORK * Note! This is another case where flexiblity is great, but can be dangerous if you don't pay attention. Setting ZIPLAB= to oh, say the root directory of your boot drive - would have results which may cause you to think poorly of my program (and I of your mental capacity). IV. Using GIFTEST with ZipLab ZipLab does not pass any default parameters at all to Giftest.Exe. You will need to do that by specifing the parameters on the line in ZLAB000.CFG which is for this purpose. If all you want to do is test .GIF files for integrity, and make sure they pass some standard of resolution and colors that you set, This is all pretty easy. Just use: /M:640X480X256 (replace the resolution and colors with yours) Giftest will work just fine with a simple parameter line like this. If you want to insert the resolution/colors into the PCBoard description, it gets a bit tricky... The first thing you have to tell Giftest is what board type you are running, so follow the parms above (no spaces) with: /B:x (Where "x" is a "1" for ProDoor or a "2" for PCBoard) Now we need to tell Giftest where the description file is for the node you are on. This is the tricky part... To do this, you are GOING TO HAVE TO HAVE A DIFFERENT ZLAB000.CFG FILE FOR EACH NODE. Follow the parms above (no spaces) with: /F:drive:\path\description.file Now in PCBoard, that is going to be the drive and directory which is specified on line 179 of PCBoard.Dat, and then the filename of UPDESC.x where "x" is replaced with the node number for the current node. (just use UPDESC without an extension if you are not running nodes) In Prodoor, the path will be your PCB home directory FOR THAT NODE, and the filename will be $DOOR.NAM. Please do not use the "/E" parameter on the Giftest parameter line. ZipLab will take care of the file if it fails, there is no need to have Giftest erase the file, and it will only confuse ZipLab. You will then have to do this for each node you have, and they will have to be in different directories. I recommend that you use something like C:\ZIPLAB\NODE1 as a directory to hold your node 1 .CFG files. All the other files for ZipLab with the exception of the ZLABxxx.CFG files can still be shared and can reside in C:\ZIPLAB or wherever you have specified in the .CFG files. Pg15 Then change your ZLAB command line in PCBTEST.BAT to something this for node 1: PCBoard: ZLAB %1 %PCBDRIVE%%PCBDIR% C:\ZIPLAB\NODE1 %2 ProDoor: ZLAB %TARGET% %pcbdrive%%pcbdir% C:\ZIPLAB\NODE1 The other option is to put the ZLABxxx.CFG files in the home PCB directory for each node, and then the command line is simple: PCBoard: ZLAB %1 %PCBDRIVE%%PCBDIR% %PCBDRIVE%%PCBDIR% %2 ProDoor: ZLAB %TARGET% %pcbdrive%%pcbdir% %pcbdrive%%pcbdir% Pg16 ############################################################################## SOME NOTES ON MEMORY USAGE ############################################################################## * NOTE! Since PCBoard is SHELLING out to run PCBTEST.BAT, there is limited memory available for ZLAB.EXE. If you are running in a multitasking or other memory constrained situation, ZLAB may not work! You should have at least 250k free memory when shelled out of PCBoard. If this is a problem, you may want to consider the VAROOM (overlay) version of PCBoard, which runs in considerably less memory than the standard PCB.EXE. The other option is to run PCBoard with the SET PCB = /SWAP environment variable. This will cause PCBoard to "swap" its code to the best available storage (EMS, DISK) whenever a SHELL function (external protocol, viewfile, and even DOORS if you have the SHELL column in DOORS.DAT(LST) set to "Y") is called. This method will cause a slight delay when SHELLING, but will provide the largest amount of available DOS memory for your external code. Pg17 ############################################################################## PRODOOR DIFFERENCES ############################################################################## * PRODOOR SYSOPS - You will need to set up your PROUTEST.BAT file like this: @echo off rem -- process test uploads request - for ProDOOR 3.44 rem -- %1-logfile, %2-testdir, %3-comport rem -- test each uploaded file individually proecho %3 ~~Testing uploads. Please wait...~ SET PCBDOOR=PRODOOR for %f in (%2\*.*) do COMMAND /c ZLAB %f d:\pcbpath d:\path\cfgpath SET PCBDOOR= :end Be sure you have enough ENVIRONMENT space to set up the PCBDOOR variable. If you are using DesqView, you may want to set PCBDOOR=xxxxxxx in your AUTOEXEC.BAT to be sure enough room is allocated in your DesqView partitions for this variable. The x's will be replaced by PRODOOR when PROUTEST.BAT is executed. I need this variable set to "PRODOOR", or ZLAB won't know you are running out of ProDoor. You don't want to leave it set to PRODOOR though, since this could confuse things for other doors/processes. Thus the "SET PCBDOOR=" line. ZipLab will fully work with ProDoor, including display/modification of the file descriptions. * Note! Sam Smith has included an example PROUTEST.BAT/PROUT1.BAT with ProDoor, which as of this writing shows how to use ZipLab Plus 1.9c to do testing. This WILL NOT work with ZipLab Plus 2.0, as the command line parameters for ZipLab have changed. Here is the relevant portion of PROUT1.BAT (called by PROUTEST.BAT). rem -- test archives using ziplab plus by jeffrey s. morley rem -- ziplab plus tests zip, arj, and lzh files :test addbidir %pcbdrive%%pcbdir%\$door.nam %TARGET% tm /l ptest %TARGET% u:\prod\ptest%PCBNODE%.cfg >>u:\prod\test%PCBNODE%.log set PCBDOOR=PRODOOR set ZIPLAB=T:\PTEST%PCBNODE% cdto t:\scr%PCBNODE% ! ptest %TARGET% u:\prod\ptest%PCBNODE%.cfg cdto u:\prod set PCBDOOR= if not exist %TARGET% del %dszlog% if not exist %TARGET% goto end :end Pg18 The line I have marked with an "!" is the command line for ZLAB.EXE and MUST be changed to read: zlab %TARGET% %pcbdrive%%pcbdir% u:\prod if you are going to use the sample PROUTEST/PROUT1 batch files from Sam. Pg19 ############################################################################## VERSION HISTORY (NEWEST TO OLDEST) ############################################################################## ZipLab Plus Beta 2.·.1 Version 2.0 beta version December 27, 1992 First release of version 2.0 to wide-area beta. Please, Please! read the documentation carefully, as well as the BETA.DOC file included. Significant changes have been made to every part of ZipLab Plus, and none of your old executables or configurations will work without replacement or modification. Pg20 ############################################################################## ABOUT ZIPLAB PLUS AND THE AUTHOR ############################################################################## ZipLab Plus started out as a somewhat complicated batch file sometime in 1989. We all had been running PKUNZIP -t against uploads for some time, but I wanted a batch file that would do a bit more, like use SCAN to test for virus infection, reject old archives, and strip out .ZIP comments. I also wanted to present an interesting interface to the user, letting him/her know what was going on in the program. As the functions in ZipLab increased and became more complicated, it took longer and longer to test files in the somewhat inefficient batch file environment. I then decided to port the program over to my programming language of choice (or at least default) QuickBasic 4.5. At this time I decided to make the program "shareware" to compensate for at least some of the time I was spending on the program. I must say that ZipLab Plus has exceeded my expectations as a shareware offering, and I am grateful (and a little stunned) for the response by Sysops who have registered the program. I had always heard figures like "only 5% or less of those who use shareware register", but if this is true then 10's of thousands of sysops are currently using ZipLab Plus. I don't believe that to be the case, and am instead inclined to believe that sysops, unlike doctors and lawyers, are NOT their own worst customers. This program was written in QuickBasic 4.5, with some help from Hammerly Computing's ProBas 4.01 and various home-grown assembly and C routines. I have included a few utilities which ZLAB will use in the course of testing. These utilities are the property of the authors, and you are strongly requested to register them if you continue to use ZIPLAB PLUS. Jeffrey S. Morley The Interconnect BBS (703)425-2505 PLEASE SEE REGISTER.DOC FOR REGISTRATION INFORMATION (C)Copyright 1989-1993 by Jeffrey S. Morley